Multiple channel transmission in MMW WLAN systems

ABSTRACT

Multiple channel transmission in mmW Wireless Local Area Network (WLAN) systems may be provided. Multi-channel aggregation and channel bonding may include, for example, multi-channel aggregation for a single transmitter/receiver pair or multi-channel aggregation and bonding for multiple transmitter/receiver pairs with frequency and space based multiple access. Multi-channel beamforming may include, for example, one analog beam across two channels and analog circuits on each channel or a single analog circuit on both channels, one analog beam across two channels and separate digital precoding schemes on each channel, one analog beam across a primary channel and separate digital precoding schemes on each channel or two analog beams on two channels and separate digital precoding on each channel. Preamble signaling may be provided.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is the U.S. National Stage, under 35 U.S.C. § 371, ofInternational Application No. PCT/US2017/050609 filed Sep. 8, 2017,which claims the benefit of U.S. Provisional Application Ser. No.62/385,081 filed Sep. 8, 2016, and U.S. Provisional Application Ser. No.62/442,771 filed Jan. 5, 2017, the contents of which are incorporated byreference herein, and this application claims benefit of the filing dateof these priority applications.

BACKGROUND

A Wireless Local Area Network (WLAN) may have multiple modes ofoperation, such as an Infrastructure Basic Service Set (BSS) mode and anIndependent BSS (IBSS) mode. A WLAN in Infrastructure BSS mode may havean Access Point (AP) for the BSS. One or more wireless transmit receiveunits (WTRUs), e.g., stations (STAs), may be associated with an AP. AnAP may have access or an interface to a Distribution System (DS) orother type of wired/wireless network that carries traffic in and out ofa BSS. Traffic to STAs that originates from outside a BSS may arrivethrough an AP, which may deliver the traffic to the STAs. STA to STAcommunication may occur in a WLAN system. An AP may act in the role of aSTA in a WLAN system. Beamforming may be used by WLAN devices.

SUMMARY

Systems, methods, and instrumentalities are disclosed for multiplechannel transmission in mmW WLAN systems. Multi-channel aggregation andchannel bonding may comprise, for example, multi-channel aggregation fora single transmitter/receiver pair or multi-channel aggregation andbonding for multiple transmitter/receiver pairs with frequency and spacebased multiple access. Multi-channel beamforming may comprise, forexample, one analog beam across two channels and analog circuits on eachchannel or a single analog circuit on both channels, one analog beamacross two channels and separate digital precoding schemes on eachchannel, one analog beam across a primary channel and separate digitalprecoding schemes on each channel or two analog beams on two channelsand separate digital precoding on each channel. Preamble signaling maybe provided.

A device (e.g., a STA or an AP) may determine to transmit an enhanceddirectional multi-gigabit (EDMG) packet frame in place of a directionalmulti-gigabit (DMG) packet. The DMG packet may include a DMGBRP-receiver (BRP-RX) packet. The EDMG frame may include a legacy-header(L-header). The L-header may include a length field. The device maydetermine a value of the length field. When the value of the lengthfield is used to calculate a transmitter time (TXTIME), the TXTIME maybe approximately the same duration as a EDMG packet frame duration. Thedevice may send the EDMG packet frame with the length field of theL-header set to the determined value. Reserved bit 46 in the L-headermay be set to a value of 1. The device may be configured to determine aduration associated with the EDMG packet frame. The EDMG packet framemay include one or more of the following: an L-header packet type field,an L-header beam tracking requested field, and/or a packet type field.The EDMG packet frame may be a DMG single carrier (SC) physical (PHY)frame.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a system diagram illustrating an example communicationssystem in which one or more disclosed embodiments may be implemented.

FIG. 1B is a system diagram illustrating an example wirelesstransmit/receive unit (WTRU) that may be used within the communicationssystem illustrated in FIG. 1A according to an embodiment.

FIG. 10 is a system diagram illustrating an example radio access network(RAN) and an example core network (CN) that may be used within thecommunications system illustrated in FIG. 1A according to an embodiment.

FIG. 1D is a system diagram illustrating a further example RAN and afurther example CN that may be used within the communications systemillustrated in FIG. 1A according to an embodiment.

FIG. 2 is an example of sector level sweep (SLS) training.

FIG. 3 is an example format for a sector sweep (SSW) frame.

FIG. 4 is an example format for a SSW field in a SSW frame.

FIG. 5 is an example of a SSW feedback field in a SSW frame.

FIG. 6 is an example physical (PHY) layer convergence procedure (PLOP)protocol data unit (PPDU) carrying a beam refinement protocol (BRP)frame and training (TRN) fields.

FIG. 7 is an example of a directional multi gigabit (DMG) PPDU format.

FIG. 8 is an example of channel bonding versus aggregation framework.

FIG. 9 provides examples of channel bonding.

FIG. 10 is an example of channelization.

FIG. 11 is an example of an enhanced DMG (EDMG) preamble format.

FIG. 12 is an example of an EDMG preamble for multi-channel multi-streamtransmissions.

FIG. 13 is an example of EDMG-short training field (STF).

FIG. 14 is an example of channel aggregation and bonding in 802.11ay.

FIG. 15 is an example of channel bonding with frequency-based multipleaccess using OFDMA.

FIG. 16 is an example of channel aggregation with frequency-basedmultiple access using SC and OFDMA.

FIG. 17 is an example of channel aggregation with a single carriertransmission and multiple spatial beams.

FIG. 18 is an example of channel bonding with OFDMA and multiple spatialbeams per sub-channel.

FIG. 19 is an example of channel aggregation with OFDMA and multiplespatial beams per sub-channel.

FIG. 20 is an example of a broadband beamformer.

FIG. 21 is an example procedure for analog beamforming.

FIG. 22 is an example procedure for hybrid beamforming.

FIG. 23 is an example procedure for one analog beam across two channels.

FIG. 24 is an example procedure for one analog beam across a primarychannel.

FIG. 25 is an example of two analog beams on two channels.

FIG. 26 is an example of two consecutive channels within the coherencebandwidth.

FIG. 27 is an example of two analog beams on two channels.

FIG. 28 is an example of two consecutive channels within the coherencebandwidth.

FIG. 29 is an example of time-division MU.

DETAILED DESCRIPTION

A detailed description of illustrative embodiments will now be describedwith reference to the various Figures. Although this descriptionprovides a detailed example of possible implementations, it should benoted that the details are intended to be exemplary and in no way limitthe scope of the application.

FIG. 1A is a diagram illustrating an example communications system 100in which one or more disclosed embodiments may be implemented. Thecommunications system 100 may be a multiple access system that providescontent, such as voice, data, video, messaging, broadcast, etc., tomultiple wireless users. The communications system 100 may enablemultiple wireless users to access such content through the sharing ofsystem resources, including wireless bandwidth. For example, thecommunications systems 100 may employ one or more channel accessmethods, such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tailunique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM(UW-OFDM), resource block-filtered OFDM, filter bank multicarrier(FBMC), and the like.

As shown in FIG. 1A, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a RAN104/113, a CN 106/115, a public switched telephone network (PSTN) 108,the Internet 110, and other networks 112, though it will be appreciatedthat the disclosed embodiments contemplate any number of WTRUs, basestations, networks, and/or network elements. Each of the WTRUs 102 a,102 b, 102 c, 102 d may be any type of device configured to operateand/or communicate in a wireless environment. By way of example, theWTRUs 102 a, 102 b, 102 c, 102 d, any of which may be referred to as a“station” and/or a “STA”, may be configured to transmit and/or receivewireless signals and may include a user equipment (UE), a mobilestation, a fixed or mobile subscriber unit, a subscription-based unit, apager, a cellular telephone, a personal digital assistant (PDA), asmartphone, a laptop, a netbook, a personal computer, a wireless sensor,a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watchor other wearable, a head-mounted display (HMD), a vehicle, a drone, amedical device and applications (e.g., remote surgery), an industrialdevice and applications (e.g., a robot and/or other wireless devicesoperating in an industrial and/or an automated processing chaincontexts), a consumer electronics device, a device operating oncommercial and/or industrial wireless networks, and the like. Any of theWTRUs 102 a, 102 b, 102 c and 102 d may be interchangeably referred toas a UE.

The communications systems 100 may also include a base station 114 aand/or a base station 114 b. Each of the base stations 114 a, 114 b maybe any type of device configured to wirelessly interface with at leastone of the WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to oneor more communication networks, such as the CN 106/115, the Internet110, and/or the other networks 112. By way of example, the base stations114 a, 114 b may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller,an access point (AP), a wireless router, and the like. While the basestations 114 a, 114 b are each depicted as a single element, it will beappreciated that the base stations 114 a, 114 b may include any numberof interconnected base stations and/or network elements.

The base station 114 a may be part of the RAN 104/113, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, etc. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals on one or morecarrier frequencies, which may be referred to as a cell (not shown).These frequencies may be in licensed spectrum, unlicensed spectrum, or acombination of licensed and unlicensed spectrum. A cell may providecoverage for a wireless service to a specific geographical area that maybe relatively fixed or that may change over time. The cell may furtherbe divided into cell sectors. For example, the cell associated with thebase station 114 a may be divided into three sectors. Thus, in oneembodiment, the base station 114 a may include three transceivers, i.e.,one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and mayutilize multiple transceivers for each sector of the cell. For example,beamforming may be used to transmit and/or receive signals in desiredspatial directions.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet(UV), visible light, etc.). The air interface 116 may be establishedusing any suitable radio access technology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104/113 and the WTRUs 102 a,102 b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA), whichmay establish the air interface 115/116/117 using wideband CDMA (WCDMA).WCDMA may include communication protocols such as High-Speed PacketAccess (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-SpeedDownlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access(HSUPA).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as Evolved UMTS TerrestrialRadio Access (E-UTRA), which may establish the air interface 116 usingLong Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/orLTE-Advanced Pro (LTE-A Pro).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as NR Radio Access, which mayestablish the air interface 116 using New Radio (NR).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement multiple radio access technologies. For example, thebase station 114 a and the WTRUs 102 a, 102 b, 102 c may implement LTEradio access and NR radio access together, for instance using dualconnectivity (DC) principles. Thus, the air interface utilized by WTRUs102 a, 102 b, 102 c may be characterized by multiple types of radioaccess technologies and/or transmissions sent to/from multiple types ofbase stations (e.g., a eNB and a gNB).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.11 (i.e.,Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperabilityfor Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×, CDMA2000 EV-DO,Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), InterimStandard 856 (IS-856), Global System for Mobile communications (GSM),Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and thelike.

The base station 114 b in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, an industrialfacility, an air corridor (e.g., for use by drones), a roadway, and thelike. In one embodiment, the base station 114 b and the WTRUs 102 c, 102d may implement a radio technology such as IEEE 802.11 to establish awireless local area network (WLAN). In an embodiment, the base station114 b and the WTRUs 102 c, 102 d may implement a radio technology suchas IEEE 802.15 to establish a wireless personal area network (WPAN). Inyet another embodiment, the base station 114 b and the WTRUs 102 c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE,LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. Asshown in FIG. 1A, the base station 114 b may have a direct connection tothe Internet 110. Thus, the base station 114 b may not be required toaccess the Internet 110 via the CN 106/115.

The RAN 104/113 may be in communication with the CN 106/115, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. The data may have varying qualityof service (QoS) requirements, such as differing throughputrequirements, latency requirements, error tolerance requirements,reliability requirements, data throughput requirements, mobilityrequirements, and the like. The CN 106/115 may provide call control,billing services, mobile location-based services, pre-paid calling,Internet connectivity, video distribution, etc., and/or performhigh-level security functions, such as user authentication. Although notshown in FIG. 1A, it will be appreciated that the RAN 104/113 and/or theCN 106/115 may be in direct or indirect communication with other RANsthat employ the same RAT as the RAN 104/113 or a different RAT. Forexample, in addition to being connected to the RAN 104/113, which may beutilizing a NR radio technology, the CN 106/115 may also be incommunication with another RAN (not shown) employing a GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN 106/115 may also serve as a gateway for the WTRUs 102 a, 102 b,102 c, 102 d to access the PSTN 108, the Internet 110, and/or the othernetworks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) and/orthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired and/or wireless communications networksowned and/or operated by other service providers. For example, thenetworks 112 may include another CN connected to one or more RANs, whichmay employ the same RAT as the RAN 104/113 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities (e.g., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks). For example, the WTRU 102 c shown in FIG. 1A may be configuredto communicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 1B is a system diagram illustrating an example WTRU 102. As shownin FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120,a transmit/receive element 122, a speaker/microphone 124, a keypad 126,a display/touchpad 128, non-removable memory 130, removable memory 132,a power source 134, a global positioning system (GPS) chipset 136,and/or other peripherals 138, among others. It will be appreciated thatthe WTRU 102 may include any sub-combination of the foregoing elementswhile remaining consistent with an embodiment.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs)circuits, any other type of integrated circuit (10), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 1Bdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In an embodiment, the transmit/receiveelement 122 may be an emitter/detector configured to transmit and/orreceive IR, UV, or visible light signals, for example. In yet anotherembodiment, the transmit/receive element 122 may be configured totransmit and/or receive both RF and light signals. It will beappreciated that the transmit/receive element 122 may be configured totransmit and/or receive any combination of wireless signals.

Although the transmit/receive element 122 is depicted in FIG. 1B as asingle element, the WTRU 102 may include any number of transmit/receiveelements 122. More specifically, the WTRU 102 may employ MIMOtechnology. Thus, in one embodiment, the WTRU 102 may include two ormore transmit/receive elements 122 (e.g., multiple antennas) fortransmitting and receiving wireless signals over the air interface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as NR and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 130 and/or the removable memory 132.The non-removable memory 130 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In other embodiments, the processor 118 may accessinformation from, and store data in, memory that is not physicallylocated on the WTRU 102, such as on a server or a home computer (notshown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs and/or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, a Virtual Reality and/or Augmented Reality (VR/AR) device, anactivity tracker, and the like. The peripherals 138 may include one ormore sensors, the sensors may be one or more of a gyroscope, anaccelerometer, a hall effect sensor, a magnetometer, an orientationsensor, a proximity sensor, a temperature sensor, a time sensor; ageolocation sensor; an altimeter, a light sensor, a touch sensor, amagnetometer, a barometer, a gesture sensor, a biometric sensor, and/ora humidity sensor.

The WTRU 102 may include a full duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for both the UL (e.g., for transmission) anddownlink (e.g., for reception) may be concurrent and/or simultaneous.The full duplex radio may include an interference management unit toreduce and or substantially eliminate self-interference via eitherhardware (e.g., a choke) or signal processing via a processor (e.g., aseparate processor (not shown) or via processor 118). In an embodiment,the WRTU 102 may include a half-duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for either the UL (e.g., for transmission) or thedownlink (e.g., for reception)).

FIG. 10 is a system diagram illustrating the RAN 104 and the CN 106according to an embodiment. As noted above, the RAN 104 may employ anE-UTRA radio technology to communicate with the WTRUs 102 a, 102 b, 102c over the air interface 116. The RAN 104 may also be in communicationwith the CN 106.

The RAN 104 may include eNode-Bs 160 a, 160 b, 160 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an embodiment. The eNode-Bs 160 a, 160 b, 160c may each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the eNode-Bs 160 a, 160 b, 160 c may implement MIMO technology. Thus,the eNode-B 160 a, for example, may use multiple antennas to transmitwireless signals to, and/or receive wireless signals from, the WTRU 102a.

Each of the eNode-Bs 160 a, 160 b, 160 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the UL and/or DL, and the like. As shown in FIG. 10, the eNode-Bs 160a, 160 b, 160 c may communicate with one another over an X2 interface.

The CN 106 shown in FIG. 10 may include a mobility management entity(MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN)gateway (or PGW) 166. While each of the foregoing elements are depictedas part of the CN 106, it will be appreciated that any of these elementsmay be owned and/or operated by an entity other than the CN operator.

The MME 162 may be connected to each of the eNode-Bs 162 a, 162 b, 162 cin the RAN 104 via an S1 interface and may serve as a control node. Forexample, the MME 162 may be responsible for authenticating users of theWTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting aparticular serving gateway during an initial attach of the WTRUs 102 a,102 b, 102 c, and the like. The MME 162 may provide a control planefunction for switching between the RAN 104 and other RANs (not shown)that employ other radio technologies, such as GSM and/or WCDMA.

The SGW 164 may be connected to each of the eNode Bs 160 a, 160 b, 160 cin the RAN 104 via the S1 interface. The SGW 164 may generally route andforward user data packets to/from the WTRUs 102 a, 102 b, 102 c. The SGW164 may perform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when DL data is available forthe WTRUs 102 a, 102 b, 102 c, managing and storing contexts of theWTRUs 102 a, 102 b, 102 c, and the like.

The SGW 164 may be connected to the PGW 166, which may provide the WTRUs102 a, 102 b, 102 c with access to packet-switched networks, such as theInternet 110, to facilitate communications between the WTRUs 102 a, 102b, 102 c and IP-enabled devices.

The CN 106 may facilitate communications with other networks. Forexample, the CN 106 may provide the WTRUs 102 a, 102 b, 102 c withaccess to circuit-switched networks, such as the PSTN 108, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and traditionalland-line communications devices. For example, the CN 106 may include,or may communicate with, an IP gateway (e.g., an IP multimedia subsystem(IMS) server) that serves as an interface between the CN 106 and thePSTN 108. In addition, the CN 106 may provide the WTRUs 102 a, 102 b,102 c with access to the other networks 112, which may include otherwired and/or wireless networks that are owned and/or operated by otherservice providers.

Although the WTRU is described in FIGS. 1A-1D as a wireless terminal, itis contemplated that in certain representative embodiments that such aterminal may use (e.g., temporarily or permanently) wired communicationinterfaces with the communication network.

In representative embodiments, the other network 112 may be a WLAN.

A WLAN in Infrastructure Basic Service Set (BSS) mode may have an AccessPoint (AP) for the BSS and one or more stations (STAs) associated withthe AP. The AP may have an access or an interface to a DistributionSystem (DS) or another type of wired/wireless network that carriestraffic in to and/or out of the BSS. Traffic to STAs that originatesfrom outside the BSS may arrive through the AP and may be delivered tothe STAs. Traffic originating from STAs to destinations outside the BSSmay be sent to the AP to be delivered to respective destinations.Traffic between STAs within the BSS may be sent through the AP, forexample, where the source STA may send traffic to the AP and the AP maydeliver the traffic to the destination STA. The traffic between STAswithin a BSS may be considered and/or referred to as peer-to-peertraffic. The peer-to-peer traffic may be sent between (e.g., directlybetween) the source and destination STAs with a direct link setup (DLS).In certain representative embodiments, the DLS may use an 802.11e DLS oran 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS)mode may not have an AP, and the STAs (e.g., all of the STAs) within orusing the IBSS may communicate directly with each other. The IBSS modeof communication may sometimes be referred to herein as an “ad-hoc” modeof communication.

When using the 802.11ac infrastructure mode of operation or a similarmode of operations, the AP may transmit a beacon on a fixed channel,such as a primary channel. The primary channel may be a fixed width(e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.The primary channel may be the operating channel of the BSS and may beused by the STAs to establish a connection with the AP. In certainrepresentative embodiments, Carrier Sense Multiple Access with CollisionAvoidance (CSMA/CA) may be implemented, for example in 802.11 systems.For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense theprimary channel. If the primary channel is sensed/detected and/ordetermined to be busy by a particular STA, the particular STA may backoff. One STA (e.g., only one station) may transmit at any given time ina given BSS.

High Throughput (HT) STAs may use a 40 MHz wide channel forcommunication, for example, via a combination of the primary 20 MHzchannel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHzwide channel.

Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz,and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may beformed by combining contiguous 20 MHz channels. A 160 MHz channel may beformed by combining 8 contiguous 20 MHz channels, or by combining twonon-contiguous 80 MHz channels, which may be referred to as an 80+80configuration. For the 80+80 configuration, the data, after channelencoding, may be passed through a segment parser that may divide thedata into two streams. Inverse Fast Fourier Transform (IFFT) processing,and time domain processing, may be done on each stream separately. Thestreams may be mapped on to the two 80 MHz channels, and the data may betransmitted by a transmitting STA. At the receiver of the receiving STA,the above described operation for the 80+80 configuration may bereversed, and the combined data may be sent to the Medium Access Control(MAC).

Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. Thechannel operating bandwidths, and carriers, are reduced in 802.11af and802.11ah relative to those used in 802.11n, and 802.11ac. 802.11afsupports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space(TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and16 MHz bandwidths using non-TVWS spectrum. According to a representativeembodiment, 802.11ah may support Meter Type Control/Machine-TypeCommunications, such as MTC devices in a macro coverage area. MTCdevices may have certain capabilities, for example, limited capabilitiesincluding support for (e.g., only support for) certain and/or limitedbandwidths. The MTC devices may include a battery with a battery lifeabove a threshold (e.g., to maintain a very long battery life).

WLAN systems, which may support multiple channels, and channelbandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include achannel which may be designated as the primary channel. The primarychannel may have a bandwidth equal to the largest common operatingbandwidth supported by all STAs in the BSS. The bandwidth of the primarychannel may be set and/or limited by a STA, from among all STAs inoperating in a BSS, which supports the smallest bandwidth operatingmode. In the example of 802.11ah, the primary channel may be 1 MHz widefor STAs (e.g., MTC type devices) that support (e.g., only support) a 1MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.Carrier sensing and/or Network Allocation Vector (NAV) settings maydepend on the status of the primary channel. If the primary channel isbusy, for example, due to a STA (which supports only a 1 MHz operatingmode), transmitting to the AP, the entire available frequency bands maybe considered busy even though a majority of the frequency bands remainsidle and may be available.

In the United States, the available frequency bands, which may be usedby 802.11ah, are from 902 MHz to 928 MHz. In Korea, the availablefrequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the availablefrequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidthavailable for 802.11ah is 6 MHz to 26 MHz depending on the country code.

FIG. 1D is a system diagram illustrating the RAN 113 and the CN 115according to an embodiment. As noted above, the RAN 113 may employ an NRradio technology to communicate with the WTRUs 102 a, 102 b, 102 c overthe air interface 116. The RAN 113 may also be in communication with theCN 115.

The RAN 113 may include gNBs 180 a, 180 b, 180 c, though it will beappreciated that the RAN 113 may include any number of gNBs whileremaining consistent with an embodiment. The gNBs 180 a, 180 b, 180 cmay each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the gNBs 180 a, 180 b, 180 c may implement MIMO technology. For example,gNBs 180 a, 108 b may utilize beamforming to transmit signals to and/orreceive signals from the gNBs 180 a, 180 b, 180 c. Thus, the gNB 180 a,for example, may use multiple antennas to transmit wireless signals to,and/or receive wireless signals from, the WTRU 102 a. In an embodiment,the gNBs 180 a, 180 b, 180 c may implement carrier aggregationtechnology. For example, the gNB 180 a may transmit multiple componentcarriers to the WTRU 102 a (not shown). A subset of these componentcarriers may be on unlicensed spectrum while the remaining componentcarriers may be on licensed spectrum. In an embodiment, the gNBs 180 a,180 b, 180 c may implement Coordinated Multi-Point (CoMP) technology.For example, WTRU 102 a may receive coordinated transmissions from gNB180 a and gNB 180 b (and/or gNB 180 c).

The WTRUs 102 a, 102 b, 102 c may communicate with gNBs 180 a, 180 b,180 c using transmissions associated with a scalable numerology. Forexample, the OFDM symbol spacing and/or OFDM subcarrier spacing may varyfor different transmissions, different cells, and/or different portionsof the wireless transmission spectrum. The WTRUs 102 a, 102 b, 102 c maycommunicate with gNBs 180 a, 180 b, 180 c using subframe or transmissiontime intervals (TTIs) of various or scalable lengths (e.g., containingvarying number of OFDM symbols and/or lasting varying lengths ofabsolute time).

The gNBs 180 a, 180 b, 180 c may be configured to communicate with theWTRUs 102 a, 102 b, 102 c in a standalone configuration and/or anon-standalone configuration. In the standalone configuration, WTRUs 102a, 102 b, 102 c may communicate with gNBs 180 a, 180 b, 180 c withoutalso accessing other RANs (e.g., such as eNode-Bs 160 a, 160 b, 160 c).In the standalone configuration, WTRUs 102 a, 102 b, 102 c may utilizeone or more of gNBs 180 a, 180 b, 180 c as a mobility anchor point. Inthe standalone configuration, WTRUs 102 a, 102 b, 102 c may communicatewith gNBs 180 a, 180 b, 180 c using signals in an unlicensed band. In anon-standalone configuration WTRUs 102 a, 102 b, 102 c may communicatewith/connect to gNBs 180 a, 180 b, 180 c while also communicatingwith/connecting to another RAN such as eNode-Bs 160 a, 160 b, 160 c. Forexample, WTRUs 102 a, 102 b, 102 c may implement DC principles tocommunicate with one or more gNBs 180 a, 180 b, 180 c and one or moreeNode-Bs 160 a, 160 b, 160 c substantially simultaneously. In thenon-standalone configuration, eNode-Bs 160 a, 160 b, 160 c may serve asa mobility anchor for WTRUs 102 a, 102 b, 102 c and gNBs 180 a, 180 b,180 c may provide additional coverage and/or throughput for servicingWTRUs 102 a, 102 b, 102 c.

Each of the gNBs 180 a, 180 b, 180 c may be associated with a particularcell (not shown) and may be configured to handle radio resourcemanagement decisions, handover decisions, scheduling of users in the ULand/or DL, support of network slicing, dual connectivity, interworkingbetween NR and E-UTRA, routing of user plane data towards User PlaneFunction (UPF) 184 a, 184 b, routing of control plane informationtowards Access and Mobility Management Function (AMF) 182 a, 182 b andthe like. As shown in FIG. 1D, the gNBs 180 a, 180 b, 180 c maycommunicate with one another over an Xn interface.

The CN 115 shown in FIG. 1D may include at least one AMF 182 a, 182 b,at least one UPF 184 a, 184 b, at least one Session Management Function(SMF) 183 a, 183 b, and possibly a Data Network (DN) 185 a, 185 b. Whileeach of the foregoing elements are depicted as part of the CN 115, itwill be appreciated that any of these elements may be owned and/oroperated by an entity other than the CN operator.

The AMF 182 a, 182 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N2 interface and may serve as acontrol node. For example, the AMF 182 a, 182 b may be responsible forauthenticating users of the WTRUs 102 a, 102 b, 102 c, support fornetwork slicing (e.g., handling of different PDU sessions with differentrequirements), selecting a particular SMF 183 a, 183 b, management ofthe registration area, termination of NAS signaling, mobilitymanagement, and the like. Network slicing may be used by the AMF 182 a,182 b in order to customize CN support for WTRUs 102 a, 102 b, 102 cbased on the types of services being utilized WTRUs 102 a, 102 b, 102 c.For example, different network slices may be established for differentuse cases such as services relying on ultra-reliable low latency (URLLC)access, services relying on enhanced massive mobile broadband (eMBB)access, services for machine type communication (MTC) access, and/or thelike. The AMF 162 may provide a control plane function for switchingbetween the RAN 113 and other RANs (not shown) that employ other radiotechnologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP accesstechnologies such as WiFi.

The SMF 183 a, 183 b may be connected to an AMF 182 a, 182 b in the CN115 via an N11 interface. The SMF 183 a, 183 b may also be connected toa UPF 184 a, 184 b in the CN 115 via an N4 interface. The SMF 183 a, 183b may select and control the UPF 184 a, 184 b and configure the routingof traffic through the UPF 184 a, 184 b. The SMF 183 a, 183 b mayperform other functions, such as managing and allocating UE IP address,managing PDU sessions, controlling policy enforcement and QoS, providingdownlink data notifications, and the like. A PDU session type may beIP-based, non-IP based, Ethernet-based, and the like.

The UPF 184 a, 184 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N3 interface, which may provide theWTRUs 102 a, 102 b, 102 c with access to packet-switched networks, suchas the Internet 110, to facilitate communications between the WTRUs 102a, 102 b, 102 c and IP-enabled devices. The UPF 184, 184 b may performother functions, such as routing and forwarding packets, enforcing userplane policies, supporting multi-homed PDU sessions, handling user planeQoS, buffering downlink packets, providing mobility anchoring, and thelike.

The CN 115 may facilitate communications with other networks. Forexample, the CN 115 may include, or may communicate with, an IP gateway(e.g., an IP multimedia subsystem (IMS) server) that serves as aninterface between the CN 115 and the PSTN 108. In addition, the CN 115may provide the WTRUs 102 a, 102 b, 102 c with access to the othernetworks 112, which may include other wired and/or wireless networksthat are owned and/or operated by other service providers. In oneembodiment, the WTRUs 102 a, 102 b, 102 c may be connected to a localData Network (DN) 185 a, 185 b through the UPF 184 a, 184 b via the N3interface to the UPF 184 a, 184 b and an N6 interface between the UPF184 a, 184 b and the DN 185 a, 185 b.

In view of FIGS. 1A-1D, and the corresponding description of FIGS.1A-1D, one or more, or all, of the functions described herein withregard to one or more of: WTRU 102 a-d, Base Station 114 a-b, eNode-B160 a-c, MME 162, SGW 164, PGW 166, gNB 180 a-c, AMF 182 a-b, UPF 184a-b, SMF 183 a-b, DN 185 a-b, and/or any other device(s) describedherein, may be performed by one or more emulation devices (not shown).The emulation devices may be one or more devices configured to emulateone or more, or all, of the functions described herein. For example, theemulation devices may be used to test other devices and/or to simulatenetwork and/or WTRU functions.

The emulation devices may be designed to implement one or more tests ofother devices in a lab environment and/or in an operator networkenvironment. For example, the one or more emulation devices may performthe one or more, or all, functions while being fully or partiallyimplemented and/or deployed as part of a wired and/or wirelesscommunication network in order to test other devices within thecommunication network. The one or more emulation devices may perform theone or more, or all, functions while being temporarilyimplemented/deployed as part of a wired and/or wireless communicationnetwork. The emulation device may be directly coupled to another devicefor purposes of testing and/or may performing testing using over-the-airwireless communications.

The one or more emulation devices may perform the one or more, includingall, functions while not being implemented/deployed as part of a wiredand/or wireless communication network. For example, the emulationdevices may be utilized in a testing scenario in a testing laboratoryand/or a non-deployed (e.g., testing) wired and/or wirelesscommunication network in order to implement testing of one or morecomponents. The one or more emulation devices may be test equipment.Direct RF coupling and/or wireless communications via RF circuitry(e.g., which may include one or more antennas) may be used by theemulation devices to transmit and/or receive data.

A WLAN may have an infrastructure basic service set (BSS) mode that mayhave an access point (AP/personal BSS coordination point (PCP)) for theBSS and one or more stations (STAs) associated with the AP/PCP. AnAP/PCP may have an access or interface to a distribution system (DS) oranother type of wired and/or wireless network that may carry traffic inand out of the BSS. Traffic to STAs that may originate from outside aBSS may arrive through an AP/PCP and may be delivered to the STAs.Traffic that may originate from STAs to destinations outside the BSS maybe sent to the AP/PCP and may be delivered to the respectivedestinations. Traffic between STAs within the BSS may (e.g., also) besent through the AP/PCP where the source STA may send traffic to theAP/PCP, and the AP/PCP may deliver the traffic to the destination STA.Traffic between STAs within a BSS may be peer-to-peer traffic.Peer-to-peer traffic may be sent between source and destination STAswith a direct link setup (DLS), which may use an 802.11e DLS or an802.11z tunneled DLS (TDLS) and may be sent directly. A WLAN may use anindependent BSS (IBSS) mode. A WLAN may have no AP/PCP and/or STAs. AWLAN may communicate (e.g., directly) with another WLAN. This mode ofcommunication may be referred to as an ad-hoc mode of communication.

An AP/PCP may use an 802.11ac infrastructure mode of operation. AnAP/PCP may transmit a beacon and may do so on a fixed channel. A fixedchannel may be the primary channel. A channel may be 20 MHz wide and maybe the operating channel of the BSS. A channel may be used by STAs andmay be used to establish a connection with the AP/PCP. A (e.g.,fundamental) channel access mechanism in a 802.11 system may be carriersense multiple access with collision avoidance (CSMA/CA). A STA (e.g.,where a STA may include an AP/PCP) may sense the primary channel, forexample, in CSMA/CA. A channel may be detected to be busy. A STA mayback off, for example, when a channel is detected to be busy. A STA maytransmit at any given time in a given BSS (e.g., using CSMA/CA).

In 802.11n, high throughput (HT) STAs may use a 40 MHz wide channel forcommunication. This may be achieved, for example, by combining a primary20 MHz channel with an adjacent 20 MHz channel to form a 40 MHz widecontiguous channel.

In 802.11ac, very high throughput (VHT) STAs may support 20 MHz, 40 MHz,80 MHz, and/or 160 MHz wide channels. 40 MHz and 80 MHz channels may beformed, for example, by combining contiguous 20 MHz channels, e.g.,similar to 802.11n. A 160 MHz channel may be formed, for example, bycombining eight contiguous 20 MHz channels or by combining twonon-contiguous 80 MHz channels, which may be referred to as an 80+80configuration. Data may be channel encoded and may be passed through asegment parser (e.g., after channel encoding). A segment parser maydivide data into streams (e.g., two streams). Inverse fast Fouriertransform (IFFT) and/or time domain processing may be performed on astream (e.g., separately on each stream). One or more streams may bemapped onto a channel (e.g., each stream to a channel or two streams totwo channels). Data may be transmitted. A receiver may perform a reverseprocess, and the combined data may be sent to the MAC.

Sub 1 GHz modes of operation may be supported by 802.11af and/or802.11ah. Channel operating bandwidths and carriers may be reduced, forexample, relative to those used in 802.11n and/or 802.11ac. 802.11af maysupport, for example, 5 MHz, 10 MHz, and/or 20 MHz bandwidths in the TVWhite Space (TVWS) spectrum. 802.11ah may support, for example, 1 MHz, 2MHz, 4 MHz, 8 MHz, and/or 16 MHz bandwidths using non-TVWS spectrum. Inexamples, 802.11ah may support one or more meter typecontrol/Machine-Type Communications (MTC) devices in a macro coveragearea. MTC device(s) may have limited capabilities and may supportlimited bandwidths. MTC device(s) may support a long battery life.

WLAN systems that support multiple channels and channel widths, such as802.11n, 802.11ac, 802.11af, and/or 802.11ah, may include a channeldesignated as a primary channel. A primary channel may have a bandwidth(e.g., approximately) equal to a common operating bandwidth (e.g.,largest common operating bandwidth) supported by one or more (e.g., all)STAs in a BSS. A bandwidth of a primary channel may be limited by one ormore (e.g., all) STA operating in the BSS. A bandwidth of a primarychannel may be limited by a STA that supports the smallest bandwidthoperating mode. In examples (e.g., for 802.11ah), a primary channel maybe 1 MHz wide, for example, when there may be STAs (e.g., MTC typedevices) that (e.g., only) support a 1 MHz mode (e.g., even when theAP/PCP and other STAs in the BSS may support a 2 MHz, 4 MHz, 8 MHz, 16MHz or other channel bandwidth operating modes). Carrier sensing and/orNAV settings may depend, for example, on the status of the primarychannel. In examples, the primary channel may be busy, e.g., due to aSTA supporting (e.g., only supporting) a 1 MHz operating modetransmitting to the AP/PCP. Available frequency bands (e.g., entireavailable frequency bands) may be considered busy even though thefrequency bands (e.g., majority of frequency bands) may be idle andavailable.

Available frequency bands that may be used by 802.11ah in the UnitedStates may range from 902 MHz to 928 MHz. Available frequency bands thatmay be used in Korea may range from 917.5 MHz to 923.5 MHz. Availablefrequency bands that may be used in Japan may range from 916.5 MHz to927.5 MHz. The total bandwidth available for 802.11ah may be, forexample, 6 MHz to 26 MHz, e.g., which may depend on the country code.

802.11ac may support downlink Multi-User MIMO (MU-MIMO) transmission tomultiple STA's in the same symbol's time frame, e.g., during a downlinkOFDM symbol. Downlink MU-MIMO may be used in 802.11ah. Downlink MU-MIMO(e.g., in 802.11ac) may use the same symbol timing for multiple STA's.Interference of waveform transmissions to multiple STAs may not be anissue. One or more (e.g., all) STAs that may be involved in MU-MIMOtransmission with the AP/PCP may use the same channel or band. Theoperating bandwidth may be the smallest channel bandwidth that issupported by the STAs in the MU-MIMO transmission with the AP/PCP.

802.11ad may support MAC and PHY layers for very high throughput (VHT),e.g., in the 60 GHz band. 802.11ad may support data rates up to 7Gbits/s. 802.11ad may support (e.g., three) different modulation modes(e.g., control PHY with single carrier and spread spectrum, singlecarrier PHY and OFDM PHY). 802.11ad may use a 60 GHz unlicensed bandand/or a band that that may be available globally. At 60 GHz, wavelengthmay be 5 mm. Compact antennas or antenna arrays may be used with 60 GHz.An antenna may create narrow RF beams (e.g., at both transmitter andreceiver). Narrow RF beams may increase coverage range and may reduceinterference. The frame structure of 802.11ad may facilitate a mechanismfor beamforming training (e.g., discovery and tracking). A beamformingtraining protocol may include two components, e.g., a sector level sweep(SLS) procedure and a beam refinement protocol (BRP) procedure. An SLSprocedure may be used for (e.g., coarse) transmit and receivebeamforming training. A BRP procedure may enable (e.g., iterative)refinement of transmit and/or receive beams. MIMO transmissions (e.g.,SU-MIMO and MU-MIMO) may not be supported by 802.11ad.

FIG. 2 is an example of sector level sweep (SLS) training. SLS trainingmay be performed, for example, using a Beacon frame or a sector sweep(SSW) frame. An AP/PCP may repeat a Beacon frame with multiplebeams/sectors within each Beacon interval (BI). Multiple STAs mayperform BF training simultaneously. An AP/PCP may not be able to sweepone or more (e.g., all) sectors/beams within one BI (e.g., due to thesize of the Beacon frame). A STA may wait one or more Bls to completeinitiator sector sweep (ISS) training. Latency may occur. A SSW framemay be utilized (e.g., for point to point BF training). A SSW frame maybe transmitted (e.g., using control PHY), for example, using the SSWframe format (e.g., as shown in FIG. 3).

FIG. 3 is an example format for a selection sector sweep (SSW) frame.

FIG. 4 is an example format for a SSW field in a SSW frame.

FIG. 5 is an example of a SSW feedback field in a SSW frame.

FIG. 6 is an example Physical (PHY) Layer Convergence Procedure (PLCP)Protocol Data Unit (PPDU) carrying a beam refinement protocol (BRP)frame and training (TRN) fields. Beamforming Refinement Protocol (BRP)may be a process where a STA may improve its antenna configuration(e.g., or antenna weight vectors) (e.g., for transmission and/orreception). BRP packets may be used (e.g., in a beam refinementprocedure) to train a receiver and/or transmitter antenna. There may betwo types of BRP packets, e.g., beamforming refinement protocol receiver(BRP-RX) packets and beamforming refinement protocol transmitter(BRP-TX) packets. A BRP packet may be carried by a DMG PPDU and may befollowed by a training field. A training field may contain an AGC fieldand may contain a transmitter or receiver training field (e.g., as shownin FIG. 6).

A value of N (e.g., in FIG. 6) may be a Training Length (e.g., traininglength given in the header field). A training length may indicate thatan AGC may have 4N subfields and may indicate that the TRN-R/T field mayhave 5N subfields. A CE subfield may the same as or similar to a CEsubfield in the preamble. One or more (e.g., all) subfields in the beamtraining field may be transmitted, for example, using rotated π/2-BPSKmodulation. A BRP MAC frame may be an Action No ACK frame and may have,for example, one or more of the following fields: Category, UnprotectedDMG Action, Dialog Token, BRP Request field, DMG Beam Refinementelement, and/or Channel Measurement Feedback element 1 to ChannelMeasurement Feedback element k.

FIG. 7 is an example of a DMG PPDU format. 802.11ad may support, forexample, four PHYs, (e.g., single carrier (SC) PHY, OFDM PHY, ControlPHY, and/or low power SC PHY). PHYs may share the same packet structurewith or without sharing the same fields.

A directional multi-gigabit (DMG) header may be provided. In the SC PHY,the header may include one or more of the following fields. The headermay include a scrambler initialization field. The scrambler initiationfield may be one or more bits (e.g., 7 bits). The header may include abase modulation and coding set (MCS) field. The base MCS field may beone or more bits (e.g., 5 bits). The header may include a length field.The length field may be one or more bits (e.g., 18 bits). The header mayinclude an additional PLCP Protocol Data Unit (PPDU) field. Theadditional PPDU field may be one or more bits (e.g., 1 bit). The headermay include a packet type field. The packet type field may be one ormore bits (e.g., 1 bit). The header may include a training length field.The training length field may be one or more bits (e.g., 5 bits). Theheader may include an aggregation field. The aggregation field may beone or more bits (e.g., 1 bit). The header may include a beam trackingrequest field. The beam tracking request field may be one or more bits(e.g., 1 bit). The header may include a last received signal strengthindication (RSSI) field. The last RSSI field may one or more bits (e.g.,4 bits). The header may include a turnaround field. The turnaround fieldmay be one or more bits (e.g., 1 bit). The header may include anextended SC MCS indication field. The extended SC MCS indication fieldmay be one or more bits (e.g., 1 bit). The header may include a reservedparameter field. The reserved parameter field may be one or more bits(e.g., 3 bits). The header may include a header check sequence (HCS)parameter field. The HCS parameter field may be one or more bits (e.g.,16 bits).

An IEEE 802.11ay physical layer (PHY) and an IEEE 802.11ay medium accesscontrol layer (MAC) may have at least one mode of operation capable ofsupporting a maximum throughput of at least 20 gigabits per second(e.g., measured at the MAC data service access point) and may maintainor improve power efficiency (e.g., per station). An IEEE 802.11ayphysical layer (PHY) and IEEE 802.11ay medium access control layer (MAC)may have license-exempt bands above 45 GHz that may have backwardcompatibility and/or may coexist with directional multi-gigabit stations(e.g., legacy stations, which may be defined by IEEE 802.11ad) operatingin the same band. 802.11ay may operate in the same band as otherstandards (e.g., legacy standards). There may be backward compatibilityand/or coexistence with legacy standards in the same band.

FIG. 8 is an example of channel bonding versus aggregation framework.802.11 ay may support MIMO, channel bonding, and/or channel aggregation.

In examples of channel bonding and aggregation, a set of Tx/Rx pairs maytransmit/receiver over multiple component channels (e.g., bands). Aprimary channel (e.g., in an 802.11 system) may be a component channelon which full carrier sense (e.g., physical and virtual) may bemaintained. 802.11 functions (e.g., AP association, probing, andreassociation) may occur on a primary channel.

In examples of channel bonding, a Tx/Rx pair may use multiple componentchannels as a single transmission channel for data. In examples ofchannel aggregation, multiple component channels may be usedindependently (see, e.g., FIGS. 8 and 9).

WLANs may support channel bonding data transmission.

FIG. 9 provides examples of channel bonding.

A transmitter may (e.g., as shown in example 1 in FIG. 9) reserve amedium with independent RTS frames on the channels to be bonded. Areceiver may reply with a CTS. The transmitter may send a channel bondeddata transmission to the receiver. Indication of bonding may be placed,for example, in the RTS or in the preamble of the transmitted dataframe. The receiver may reply with a channel bonded ACK. The transmittermay reply with two CF-ENDs to end the transmit opportunity (TXOP)reservation.

A transmitter may (e.g., as shown in example 2 in FIG. 9) reserve amedium with CTS-to-self frames on the channels to be bonded. Thetransmitter may send a channel bonded data transmission to a receiver.Indication of bonding may be placed, for example, in the RTS or in thepreamble of the transmitted data frame. The receiver may reply with achannel bonded ACK.

Full carrier sense (e.g., physical and/or virtual) may be maintained ona primary channel.

An enhanced directional multi gigabit (EDMG) STA may transmit a frame toa peer EDMG STA to indicate intent to perform channel bondingtransmission to the peer STA. This may allow an EDMG STA to choose tooperate over multiple channels after receiving such a frame, which maysave power.

802.11ay may support (e.g., when using multiple channels) simultaneoustransmission by a PCP or an AP to multiple STAs allocated to differentchannels (e.g., individually).

802.11ay may support allocation of service period(s) (SP(s)) andscheduled contention-based access period(s) (CBAP(s)) over more than onechannel and/or over a bonded channel. Allocations may or may not includea primary channel. Source and destination of allocations may bedifferent, for example, when allocations over different channels overlapin time. Channels used for allocations may be limited to the operatingchannels of the BSS.

FIG. 10 is an example of channelization.

Channel bonding and channel aggregation may be supported. Examples ofchannel aggregation modes may be, for example, 2.16 GHz+2.16 GHz, 4.32GHz+4.32 GHz, and/or 4.32+2.16 GHz aggregation modes. EDMG-Header-A(e.g., a PHY header for EDMG devices) may have, for example, one or moreof the following fields: (i) bandwidth; (ii) channel bonding (e.g., todifferentiate between channel bonding and channel aggregation); and/or(iii) primary channel.

Fields may be included in a Control Trailer for RTS/CTS setup. Aduplicated RTS/CTS approach may carry the bandwidth information forefficient channel bonding operation.

FIG. 11 is an example of an EDMG preamble format.

FIG. 12 is an example of an EDMG preamble for multi-channel multi-streamtransmissions.

The EDMG preamble format may be used for multi-channel transmission withMIMO. A multi-stream transmission of a non-EDMG part of preamble mayutilize cyclic shifts.

EDMG-short training field (EDMG-STF) may support channel bonding. AnEDMG-STF field for spatial stream “i” may be built from multiplerepetitions of a Gwi sequence. Gwi may be composed of Golay sequences,where Gwi=[GaiN, GaiN, GaiN, −GaiN]. N may be a sequence length (e.g.,128, 256, and 512 for CB=1, 2, and 4, respectively). CB may refer tochannel bonding. Chip duration may be Tc=0.57 ns.

Golay sequences of length N=256, and 512 may be used for channel bondingof 2 and 4, e.g., similar to the EDMG-STF field.

An EDMG-Header_B field may be optional for MIMO transmission. A codingand modulation scheme may be used for EDMG-Header-B, for example, forsingle carrier (SC) PHY MU-MIMO. An EDMG-Header-B field may betransmitted using two SC symbol blocks.

In examples, for a (e.g., each) SC symbol block, part of coded andmodulated EDMG-Header-B symbols (e.g., refer as blki for ith stream) maybe carried by 448 chips and a Guard Interval (GI) with a Golay Gai64sequence of length 64 chips may be appended thereto. A SC symbol blockwithout channel bonding may be [Gai64, blki]. In examples, for channelbonding with 2, 3, and 4 channels, a SC symbol block may be defined,respectively as: (i) NCB=2: [Gai128, blki, blki]; (ii) NCB=3: [Gai192,blki, blki, blki]; and (iii) NCB=4: [Gai256, blki, blki, blki, blki].

Frequency-based multiple access with multi-channel transmission may beprovided. 802.11ay may support (e.g., when using multiple channels)simultaneous transmission by a PCP or an AP to multiple STAs allocatedto different channels (e.g., individually). Support (e.g., procedures)may be provided for transmission to and reception from different STAs.

Beamforming may be provided to support multi-channel transmission.

FIG. 13 is an example of EDMG-STF.

802.11 ay systems may support transmit and/or receive beam(s) thatenable single beam and/or multi-beam transmission(s) between two or morenodes. Support may be provided (e.g., with channel bonding oraggregation) for the formation of beams and transmission/reception ofcontrol information and data that account for the bandwidth coherence ofaggregated or bonded channels.

Information in the EDMG-header may be provided.

802.11ay may provide and/or perform channel aggregation and/or bondingtransmission. For example, 802.11ay may provide and/or perform channelaggregation and/or bonding transmission to one or more users on one ormore channels. A channel may include one or more MU-MIMO transmissionsto one or more STAs. Signaling may be provided to a receiver STA. Forexample, signaling may be provided to a receiver STA such that thereceiver STA may not perform (e.g., may not be required to perform)decoding for one or more PSDUs in a PPDU.

A MIMO-setup frame may precede (e.g., immediately precede) a MU PPDU.For example, a MIMO-setup frame may precede (e.g., immediately precede)a MU PPDU from a transmitter (e.g., the same transmitter). The coverageof the preamble transmitted in a preamble waveform in the MIMO-setupframe may be identical to the preamble in the MU-PPDU that follows. Thismay incur an extra overhead. The extra overhead may be avoided.

EDMG design may not identify BSS and/or TXOP information. Notidentifying BSS and/or TXOP information may have one or more of thefollowing effects.

For example, an effect may be that an intra-BSS frame may be missed. Dueto the directional nature of the 802.11ay, frames from 2 BSSs mayoverlap (e.g., may overlap in time). If frames from 2 BSS overlap (e.g.,overlap in time), a transmitter may not hear other transmitters. Forexample, for a receiving STA attempting to decode an overlapping BSS(OBSS) frame, the receiving STA may have missed a concurrent intra-BSSframe. For a SU-PPDU, the receiving STA may decode (e.g., need todecode) the data portion of the PPDU. The receiving STA may decode(e.g., need to decode) the data portion of the PPDU to determine whetherthe receiving STA may be the receiver and/or to update NAV. Thereceiving STA may decode (e.g., need to decode) the data portion of thePPDU to determine whether the receiving STA may be the receiver and/orto update NAV, even if the frame is an OBSS frame. For a MU-PPDU, anOBSS frame may have a matching association ID (AID) in EDMG-header-A.The STA with an identical AID may receive an OBSS frame and/or mayignore the intra-BSS frame.

An effect may be that the battery may be drained. For example, decodingthe data portion of an OBSS frames may drain the battery.

Multi-channel aggregation and channel bonding may be provided. Forexample, multi-channel aggregation and channel bonding may include oneor more of the following: multi-channel aggregation for a singletransmitter/receiver pair and/or multi-channel aggregation and bondingfor multiple transmitter/receiver pairs with frequency and space basedmultiple access.

FIG. 14 illustrates examples of channel aggregation and bonding in802.11ay. In examples, a transmitter may reserve a medium withindependent RTS frames on the channels to be bonded (e.g., FIG. 14A). Areceiver may reply with a CTS. The transmitter may send a channelaggregated data transmission to the receiver. An indication ofaggregation may be placed, for example, in the RTS or in the preamble ofthe transmitted data frame. The receiver may reply with two channelaggregated ACKs. The transmitter may reply with two contention-free ends(CF-ENDs) to end the TXOP reservation.

In examples, a transmitter may reserve a medium with CTS-to-self frameson the channels to be bonded, as shown in FIG. 14B. The transmitter maysend a channel aggregated data transmission to the receiver. Anindication of aggregation may be placed, for example, in the RTS or inthe preamble of the transmitted data frame. The receiver may reply withtwo channel aggregated ACKs.

Multi-channel aggregation and channel bonding may include, for example,multiple transmitter/receiver pairs with frequency- and/or space-basedmultiple access.

Examples may be provided for channel bonding and aggregation formultiple users. Multi-channel transmission procedures may allow formultiple component channels to be used in a frequency-based multipleaccess manner. For example, a STA/WTRU (e.g., the transmitter/receiverand PCP/AP or Transmission point (TRP)) may transmit or receive frommultiple STAs (e.g., the receivers/transmitters). This may be applicableto channel bonding and channel aggregation (see, e.g., FIGS. 15 and 16),which may be combined with spatial multiple access.

FIG. 15 is an example of channel bonding with frequency-based multipleaccess using OFDMA.

FIG. 16 is an example of channel aggregation with frequency-basedmultiple access using SC and OFDMA.

Frequency-based multiple access may be based on Orthogonal FrequencyDivision Multiplexing (OFDM) or Single Carrier transmission.

Single-carrier transmission with frequency-based multiple access may beapplied to aggregation (e.g., alone). A (e.g., each) component carriermay have an independent SC waveform transmitted on it. A preamble may beidentical or component specific, for example, in a downlinktransmission. A (e.g., each) preamble may be transmitted (e.g.,transmitted independently) on a (e.g., each) component channel, forexample in an uplink transmission. Transmissions may occur at a timesuch that the transmissions may arrive at the transmitter within atolerance time. A user may transmit an identical beam that may span theaggregated channels. An (e.g., each) independent user may be assigned toa bandwidth spanning a (e.g., each) component sub-channel. More than oneuser may be assigned to a sub-channel. Users may be separated (e.g.,separated spatially) based on, for example, different arrival/departuredirections and/or time delays (see, e.g., FIG. 17).

FIG. 17 is an example of channel aggregation with a single carriertransmission and multiple spatial beams.

OFDM-based transmission with frequency-based multiple access may beapplied to aggregation and bonding. A bandwidth of sub-channels may, forexample, be set to the bandwidth of a component channel or to a set ofbandwidths that may be less than the bandwidth of a (e.g., each)component channel. An (e.g., each) independent user may be assigned oneor more sub channels in the frequency domain. More than one user may beassigned to a sub-channel and may be separated (e.g., separatedspatially) based on, for example, different arrival/departure directionsand time delays (see, e.g., FIGS. 18 and 19).

FIG. 18 is an example of channel bonding with OFDMA and multiple spatialbeams per sub-channel.

FIG. 19 is an example of channel aggregation with OFDMA and multiplespatial beams per sub-channel.

Beamforming implementations may be disclosed that support multi-channeltransmission. For example, one or more of the following may apply:multi-channel beamforming; one analog beam across two channels (e.g.,analog BF training on a (e.g., each) channel) and a separate analogcircuit on a (e.g., each) channel or a single analog circuit on bothchannels; one analog beam across two channels (e.g., analog BF trainingon both channels) and separate digital precoding schemes on a (e.g.,each) channel, which may support SU; one analog beam across a primarychannel (e.g., analog BF training on primary channel only) and separatedigital precoding schemes on a (e.g., each) channel, which may supportSU; and/or two analog beams on two channels (e.g., analog BF training onboth channels) and separate digital precoding schemes on a (e.g., each)channel, which may support SU and/or MU.

Beamforming (e.g., beamforming for multi-channel transmission) may workon a (e.g., each) component channel independently or on the multiplecomponent channels as a single channel. The use of the same beam ordifferent beams over the multiple component channels may depend on, forexample, one or more of the following: (i) correlation between thespatial signatures of the multiple channels; (ii) the domain abeamformer is in; (iii) digital domain beamforming; and/or (iv) hybridbeamforming.

The use of the same beam or different beams over the multiple componentchannels may depend on a correlation between the spatial signatures ofmultiple channels. Channels whose spatial signatures are correlated maycomprise adjacent, small bandwidth channels or channels that may be lessthan a coherence bandwidth apart. The same beams may be used acrossmultiple channels without a significant loss in performance, with areduction in beamforming training, and/or feedback overhead.

Channels whose spatial signatures are not correlated may comprisechannels that may be greater than the coherence bandwidth apart. Use ofthe same beams across the channels may result in a performance loss.

The use of the same beam or different beams over the multiple componentchannels may depend on the domain a beamformer is in. Examplesassociated with analog domain beamforming may be provided.

For analog beamforming (e.g., for analog beamforming only), beams may beformed by phasors on antenna elements in the analog domain. Separatebeams per stream may be created for a (e.g., each) of the multiplechannels. One or more of the following features may apply.

A (e.g., each) channel may have an independent or separatelycontrollable physical antenna array or antenna panel. This may allow forselection of an optimal analog beam, for example, even when multiplechannels may not be within a coherence bandwidth of the physicalchannel. The granularity of analog beams may be, for example, on theorder of the bonded or aggregated channels or on the order of OFDMAsub-channels within a (e.g., each) component channel.

A (e.g., single) analog beamformer may be used across one or more (e.g.,all) of the channels. The (e.g., single) beamformer may be created basedon the primary channel.

A (e.g., single) beamformer may be created based on a combination ofcomponent channels (e.g., all the component channels). A broadbandbeamformer may have a frequency selective response matched to thechannel. A single beamformer may be followed by a broadband analogcircuit or filter made from active or passive filter components, whichmay improve performance. In examples of a broadband beamformer (e.g., asshown in FIG. 20), steering delays may be used to specify a lookdirection. A TDL structure may be used to specify a frequency responsein the look direction. Elements of the analog filter may be optimized inthe procedure. An analog filter made up of active components may be usedto construct the broadband filter.

FIG. 20 is an example of a broadband beamformer.

The use of the same beam or different beams over multiple componentchannels may depend on digital domain beamforming (e.g., digital domainbeamforming only). Digital beamforming may have more flexibility inenabling independent beamforming per channel or per sub-channel. Thismay be expensive, for example, when there may be a large number ofantennas in the phase-array antenna (PM).

The use of the same beam or different beams over the multiple componentchannels may depend on hybrid beamforming. A combination of widebandanalogue beamforming and frequency selective digital beamforming may beused. Analog beamformers may be based on the (e.g., entire) aggregatedor bonded channel, the component channels or subchannels of thecomponent channels. A digital domain beamformer may be used to correctfor errors in the analog beamformer. A digital domain beamformer mayenable its performance on the digital domain beamformer only.

Multi-channel beamforming may be provided. The multi-channel beamformingmay include one or more of the following: a modified sector sweepprocedure; a modified spatial beam refinement procedure; and/or afrequency refinement procedure.

A modified sector sweep procedure may estimate a spatial beam pairs(e.g., the best spatial beam pairs) between an initiator and a responderthat may be implemented N/N_ssw times. N_ssw may be the number ofindependent analog beams in frequency with 1<N_ssw<N. If N_ssw=N, a(e.g., each) component channel may have its own independent analog beam.In examples where N_ssw=1, one or more (e.g., all) component beams mayhave (e.g., only) one analog beam. In examples, component beams may begrouped (e.g., arbitrarily grouped), for example, where N_ssw_1≠N_ssw_2≠. . . ≠ . . . N_ssw_n and N_ssw_1+N_ssw_2+ . . . + . . . N_ssw_n=N. Thisinformation may be signaled to the STAs during the SSW setup procedure.

A modified spatial beam refinement procedure may refine the best spatialbeams (e.g., estimated best spatial beam pairs from the modified sectorsweep procedure) to a user. The procedure may be implemented N/N_brptimes. N_brp may be the number of independent analog beams in frequencywith 1<N_brp<N. If N_brp=N, a (e.g., each) component channel may haveits own independent analog beam. In examples where N_brp=1, one or more(e.g., all) the component beams may have one analog beam (e.g., only oneanalog beam). Component beams may be grouped (e.g., arbitrarilygrouped), for example, where N_brp_1≠N_brp_2≠ . . . ≠ . . . N_brp_n andN_brp_1+N_brp_2+ . . . + . . . N_brp_n=N. This information may besignaled to the STAs, e.g., during the BRP setup procedure. In examples,N_brp may be equal to N_ssw.

A frequency refinement procedure may correct mismatch between the actualchannel and the channel estimated using the refined beams. The frequencyrefinement procedure may be analog or digital.

FIG. 21 is an example procedure for analog beamforming (e.g., analogonly beamforming). In examples of an analog frequency refinementprocedure, a series of signals may be sent to enable the estimation of atime domain correlation. This information may be fed back and used toestimate the TDL or active analog filter. The number of independentanalog filters may be determined, for example, by N_analog (see, e.g.,FIG. 21).

FIG. 22 is an example procedure for hybrid beamforming. In examples of adigital frequency refinement procedure, a channel estimation or trainingfield may be sent. A representation of the instantaneous channel may befed back to enable the design for the digital precoder. The number ofindependent digital filters may be determined, for example, by N_digital(see, e.g., FIG. 22). N_analog/N_digital may differ from N_ssw.

Schemes, procedures, and their applications may be provided for singleuser, multi-user, and diversity transmission. In examples, N-componentchannels may be aggregated and/or bonded. Examples may use N=2, but theschemes and procedures may be applicable to (e.g., extendable to) N>2.

There may be one analog beam across two channels (e.g., analog BFtraining on a (e.g., each) channel) and a separate analog circuit on a(e.g., each) channel or a single analog circuit on both channels. One ormore of the following may apply: an analog beam-training procedure;spatial beam refinement; and/or multi-channel beam refinement.

An analog beam-training procedure may identify the best spatial beam(s)using a modified sector level sweep. The training procedure may identifythe best spatial beams, e.g., with multiple spatial beams. A sweep mayoccur for initiator (Tx/Rx) and responder (Tx/Rx). Finding one set ofbeams may be sufficient (e.g., Initiator Tx and Responder Rx), forexample, when a channel reciprocity assumption is valid (e.g., due tocalibration).

The system may go through (e.g., further go through) spatial beamrefinement. For example, the system may go through further spatial beamrefinement, such as a modified Beam Refinement Protocol (BRP), to refinethe analog beams.

The system may identify the spatial beams (e.g., the best spatialbeams). The system may (e.g., when the spatial beams have beenidentified) go through a multi-channel beam refinement procedure totrain and/or estimate parameters for the analog circuit. A multi-channelbeam refinement procedure may involve estimation of an array correlationmatrix (R). Matrix elements may represent the correlation betweenvarious tap outputs. The amount and frequency of feedback may be reduced(e.g., in a correlation), for example, compared with digital basebandfeedback. A feedback request may indicate whether an explicit channelfeedback or a correlation feedback may be required. Signaling may beadded to request correlation matrix feedback (e.g., which may bedifferent than channel element feedback used in a BRP feedback).

Elements of the filter may be estimated based on a desired metric.

A TDL estimation frame may be constructed to assist in the estimation ofR. A BRP frame with TRN/T and TRN/R may be re-used (e.g., to assist inthe estimation of R).

There may be one analog beam across two channels (e.g., analog BFtraining on both channels) and separate digital precoding schemes on a(e.g., each) channel, which may support SU.

A single analog beam-training procedure may identify the best spatialbeam(s), for example, using a modified sector level sweep. The trainingprocedure may identify the best spatial beams on multiple (e.g., both)component channels, for example, when there may be multiple spatialbeams. A sweep may occur for initiator (Tx/Rx) and responder (Tx/Rx).Finding one set of beams may be sufficient (e.g., Initiator Tx andResponder Rx), for example, when the channel reciprocity assumption maybe valid (e.g., due to calibration).

The system may go through (e.g., go through further) spatial beamrefinement (e.g., a modified Beam Refinement Protocol to refine theanalog beams). A (e.g., each) channel may (e.g., when the spatial beamshave been identified) go through a digital baseband channel estimationprocedure to estimate the effective digital baseband channel. Thedigital baseband channel may be fed back to the transmitter. Inexamples, the explicit channel co-efficient(s) may be fed back. Inexamples, an implicit feedback based on a codebook may be fed back. A(e.g., each) sub-channel may estimate its digital precoder (e.g., basedon a selected scheme).

FIG. 23 is an example procedure for one analog beam across two channels.One analog beam may be formed across two channels with a set of phaseshifters. One or more of the following may apply. An initiator may startan SLS with one analog beam across two channels to identify the bestspatial beam. A responder may carry out (e.g., carry out similarly) anSLS with one analog beam across two channels. Feedback and ACK may besent (e.g., sent jointly) on both channels. A beam refinement protocol(BRP) (e.g., on both channels) may be implemented, for example, whenrequested by the initiator or the responder. An effective channelestimation may be conducted based on the best beam pair, for example,when the best spatial beams are identified. The initiator may transmit achannel estimation packet on both channels. Effective channels may beestimated for both channels (e.g., independently). The responder mayfeed back the effective channel information on both channels.

There may be one analog beam across a primary channel (e.g., analog BFtraining on primary channel only) and separate digital precoding schemeson a (e.g., each) channel, which may support SU.

A single analog beam-training procedure may identify the best spatialbeam(s), for example, using a modified sector level sweep. The trainingprocedure may identify the best spatial beams based on the primarycomponent channel only, for example, when there may be multiple spatialbeams. A sweep may occur for initiator (Tx/Rx) and responder (Tx/Rx).Finding one set of beams may be sufficient (e.g., Initiator Tx andResponder Rx), for example, when the channel reciprocity assumption maybe valid (e.g., due to calibration).

The system may go through (e.g., go through further) spatial beamrefinement (e.g., a modified Beam Refinement Protocol to refine theanalog beams) on the primary component channel only. A (e.g., each)channel may (e.g., when the spatial beams have been identified) gothrough a digital baseband channel estimation procedure to estimate theeffective digital baseband channel. The analog beam for the primarychannel may be used on one or more (e.g., all) the component channels.

The digital baseband channel may be fed back to the transmitter. Inexamples, explicit channel co-efficient(s) may be fed back. In examples,an implicit feedback based on a codebook may be fed back. A (e.g., each)sub-channel may estimate its digital precoder, for example, based on aselected scheme.

FIG. 24 is an example procedure for one analog beam across a primarychannel. CH1 may be the primary channel. One analog beam may be formed,for example, based on the primary channel with a set of phase shifters.One or more of the following may apply. An initiator may start an SLSwith one analog beam across the primary channel to identify the bestspatial beam on the channel. A responder may (e.g., similarly) carry outan SLS with one analog beam for the primary channel. Feedback and ACKmay be sent on the primary channel (e.g., only on the primary channel).A beam refinement protocol (BRP) on the primary channel may occur, forexample, when requested by the initiator or the responder. An effectivechannel estimation may be conducted on both channels (e.g., based on thebest beam pair obtained from the primary channel), for example, when thebest spatial beams have been identified.

A secondary channel (e.g., channel 2) may use the beam obtained by theprimary channel (e.g., channel 1).

The initiator may transmit a channel estimation packet on both channels.Effective channels may be estimated for both channels (e.g.,independently).

The responder may feed back the effective channel information on bothchannels.

There may be two analog beams on two channels (e.g., analog BF trainingon both channels) and separate digital precoding schemes on a (e.g.,each) channel, which may support SU and/or MU.

In examples, multiple analog beam-training procedures may identify thebest spatial beam(s), e.g., using a modified sector level sweep. Atraining procedure may identify the best spatial beams for a (e.g.,each) component channel, for example, when there may be multiple spatialbeams. A sweep may occur for initiator (Tx/Rx) and responder (Tx/Rx).Finding one set of beams may be sufficient (e.g., Initiator Tx andResponder Rx), for example, when the channel reciprocity assumption maybe valid (e.g., due to calibration). The system may go through (e.g.,further go through) spatial beam refinement (e.g., a modified BeamRefinement Protocol to refine the analog beams). A (e.g., each) channelmay (e.g., when the spatial beams have been identified) go through adigital baseband channel estimation procedure to estimate the effectivedigital baseband channel. The digital baseband channel may be fed backto the transmitter. In examples, explicit channel co-efficient(s) may befed back. In examples, an implicit feedback based on a codebook may befed back.

A (e.g., each) sub-channel may estimate its digital precoder, forexample, based on a selected scheme.

FIG. 25 is an example of two analog beams on two channels. FIG. 25 showsan example of an SU situation. Two analog beams may be formed on twochannels with two sets of phase shifters. One or more of the followingmay apply. An initiator may start an SLS with two analog beams on twochannels to identify the best spatial beam (e.g., independently). Aresponder may carry out an SLS with two independent analog beams (e.g.,similarly) on two channels. Feedback and ACK may be sent (e.g., sentindependently) on both channels. A beam refinement protocol (BRP) mayoccur on both channels, for example, when requested by the initiator orthe responder. The best spatial beams may be identified. An effectivechannel estimation may be conducted (e.g., independently), for example,based on the best beam pairs for the two channels. An initiator maytransmit a channel estimation packet on both channels. Effectivechannels may be estimated for both channels (e.g., independently). Theresponder may feed back the effective channel information on bothchannels.

FIG. 26 is an example of two consecutive channels within the coherencebandwidth. Coherence bandwidth may be a statistical measurement of therange of frequencies over which the channel may be considered flat. Forexample, the approximate maximum bandwidth or frequency interval overwhich two frequencies of a signal may experience (e.g., may likely toexperience) comparable or correlated amplitude fading. Improvedbeamforming training may be adopted, for example, when two consecutivechannels within the coherence bandwidth are used. The two channels mayhave similar channel information in angular domain, which may beexploited for beamforming training. Two analog beams may be formed ontwo channels with two sets of phase shifters. One or more of thefollowing may apply. An initiator may start an SLS with two consecutiveanalog beams on two channels to identify the best spatial beam(s). A(e.g., each) channel may have an individual non-overlapped beam. Beamsmay be broadened. If the beams are broadened, SSW time may be shortenedor the sector sweeping time may be increased. A responder may carry outan SLS with two consecutive independent analog beams on two channels(e.g., similarly). Feedback and ACK may be sent (e.g., sentindependently) on the specific channel (e.g., channel 1 or 2) with thebest beam. An independent beam refinement protocol (BRP) on bothchannels may occur, for example, when requested by the initiator or theresponder. The best spatial beam(s) may be identified. An effectivechannel estimation may be conducted (e.g., conducted independently), forexample, based on the best beam pairs for the two channels. An initiatormay transmit a channel estimation packet on both channels. Effectivechannels may be estimated for both channels (e.g., independently). Theresponder may feed back the effective channel information on bothchannels.

FIG. 27 is an example of two analog beams on two channels. FIG. 27 showsan example of a frequency-division MU situation. In examples of afrequency-division multi-user situation, users may be able to hear onboth channels and may have a pre-defined channel for transmission. Inexamples, responder 1 may use channel 1, and responder 2 may use channel2. Two analog beams may be formed on two channels with two sets of phaseshifters. One or more of the following may apply. An initiator may startan SLS with two analog beams on two channels to identify the bestspatial beam(s) (e.g., independently). Responders (e.g., responder 1 andresponder 2 shown in FIG. 27) may carry out an SLS with analog beams ontheir individual channels, respectively. Feedback and ACK may be sent(e.g., sent independently) on individual channels for differentresponders. A beam refinement protocol (BRP) for both users on bothchannels may occur, for example, when requested by the initiator or theresponder. The best spatial beams may be identified. An effectivechannel estimation may be conducted, for example, based on the best beampairs of the two different channels for different users. The initiatormay transmit a channel estimation packet on both channels. Effectivechannels may be estimated on individual channels for different users(e.g., independently). Responders may feed back the effective channelinformation on individual channels, respectively.

FIG. 28 is an example of two consecutive channels within the coherencebandwidth. FIG. 28 shows an example of a frequency-division MUsituation. Improved beamforming training may be adopted, for example,when two consecutive channels within the coherence bandwidth are used.Multiple users may be able to hear on both channels. Users may have apre-defined channel for transmission. In examples, responder 1 may usechannel 1 and responder 2 may use channel 2. Two analog beams may beformed on two channels with two sets of phase shifters. One or more ofthe following may apply. An initiator may start an SLS with twoconsecutive analog beams on two channels to identify the best spatialbeam. A (e.g., each) channel may have an individual non-overlapped beam.Beams may be broadened. SSW time may be shortened or the sector sweepingtime may be increased. Responders (e.g., responder 1 and responder 2shown in FIG. 28) may carry out a SLS with analog beams on theirindividual channels, respectively. Feedback and ACK may be sent (e.g.,sent independently) on individual channels for different responders. Abeam refinement protocol (BRP) for both users on both channels mayoccur, for example, when requested by the initiator or the responder.The best spatial beam(s) may be identified. An effective channelestimation may be conducted, for example, based on the best beam pairsof the two different channels for different users. The initiator maytransmit a channel estimation packet on both channels. Effectivechannels may be estimated on individual channels for different users(e.g., independently). Responders may feed back effective channelinformation on individual channels, respectively.

FIG. 29 is an example of a time-division MU situation. In examples of atime-division multi-user situation, users may be able to use bothchannels. Two analog beams may be formed on two channels with two setsof phase shifters. Users and channels may be jointly arranged, forexample, when a (e.g., each) set of phase shifters has one (e.g., onlyone) steering direction. One or more of the following may apply. Aninitiator may start an SLS with two analog beams on two channels jointlyfor multiple (e.g., all) users.

Responders may carry out an SLS with analog beams on both channels,e.g., in a time-division manner. The initiator may identify the bestbeam for a (e.g., each) user on the dominant channel or on multiple(e.g., both) channels. Feedback and ACK may be sent (e.g., sentindependently) on selected channels for different responders, e.g., in atime-division manner. A beam refinement protocol (BRP) for both users onselected channels may occur, for example, when requested by theinitiator or the responder. The best spatial beams may be identified. Aneffective channel estimation may be conducted, for example, based on thebest beam pairs of the two different channels for different users. Aninitiator may transmit a channel estimation packet on both channels.Effective channels may be estimated on individual channels for differentusers, e.g., in a time-division manner. Responders may feed back theeffective channel information on both channels, e.g., respectively.

Channel information for an STA (e.g., each station) may be provided.

The EMG-header A may include channel assignment/allocation informationfor a user. For example, for a multi-channel multi-user transmission(e.g., a transmission involving more than one bonded/aggregated channelsand/or one or more users), the EDMG-header A may include channelassignment/allocation information for a (e.g., each) user. The channelassignment information may include the resources assigned to an STA. Forexample, the channel assignment information may include the resourcesassigned to an STA, such as Spatial Stream (SS) allocation and/orchannel/frequency information that may be conveyed to the receiving STA.

An EDMG header-A may be repeated on a channel. For example, an EDMGheader-A (e.g., an identical EDMG header-A) may be repeated on a channelthat may be occupied by the PPDU. The EDMG header B may (e.g., may only)contain information that may be relevant to a STA (e.g., the STA thatmay be assigned to the channel).

The EDMG header A on a channel may (e.g., may only) contain SS and/orchannel allocation information. For example, the EDMG header A on achannel may (e.g., may only) contain the SS and/or channel allocationinformation for a channel, such that the content of EDMG header-A may bedifferent on a channel for a (e.g., the same) PPDU.

Overhead reduction of legacy preamble in a transmission following MIMOsetup may be provided.

One or more header fields in the EDMG preamble may be omitted from thePPDU. For example, to reduce the preamble overhead following aMIMO-setup frame, one or more combinations of the first 4 header fieldsin the FIG. 11 EDMG preamble (e.g., legacy-short training field (L-STF),legacy-channel estimation field (L-CEF), L-header, EDMG-header-A) may beomitted from the PPDU that may be transmitted after the MIMO setupframe.

The information in the omitted header may be derived from the MIMO-setupframe and/or the EDMG-header B of the MU PPDU that omits the header.

The L-header length field and/or the NAV/Duration field of the MIMOsetup frame may signal a time that may include the duration of thesubsequent PPDU that may omit the headers. For example, the L-headerlength field and/or the NAV/Duration field of the MIMO setup frame maysignal a time that may include the duration of the subsequent PPDU thatmay omit the headers, such that STAs may identify an equivalent PPDUduration.

BSS identification and/or TXOP information may be provided.

BSS identification may be included in the EDMG-header A. For example,BSS identification may be included in the EDMG-header A such that anOBSS STA may ignore the PPDU. The identification may have fewer bitsthan the basic service set identifier (BSSID) (e.g., the actual BSSID).

EDMG-A header fields (e.g., legacy EDMG-A header fields) may contain theBSS identification. For example, legacy EDMG-A header fields may containthe BSS identification without additional signaling overhead. Thesignaled AID/scrambling initialization/LAST RSSI may contain a valuethat may be calculated from the BSS identifier.

TXOP information may be included in the EDMG header A. For example, TXOPinformation may be included in the EDMG header A such that the need fornon-intended STAs to decode the data portion of the frame for NAVinformation may be eliminated.

TXOP information may be signaled in the L-header length and/or traininglength fields. For example, TXOP information may be signaled in theL-header length and/or training length fields to transmit (e.g., spoof)the legacy STA (e.g., like a long packet). The EDMG STA may be based onthe PLOP service data unit (PSDU) length/MCS and/or other information toobtain the frame duration (e.g., actual frame duration).

BSS identification and/or TXOP information may be provided, e.g., usingone or more of the following mechanism(s).

An L-header for EDMG signaling may be provided.

The sender of an EDMG frame may use the training length field ofL-header to signal information useful for an EDMG receiver. Theinformation may include one or more of the following: beam relatedinformation; spatial reuse related information; and/or BSSID orcompressed BSSID.

Beam related information may enable the receiver to identify the beamchanging from L-preamble part to EDMG preamble part. Beam relatedinformation may include one or more parameters. For example, beamrelated information may include the number of PAAs; whether polarizationis utilized; and/or whether digital precoding is applied. Beam relatedinformation may (e.g., may also) include whether SISO beams, SU-MIMObeams, and/or MU-MIMO beams are used in the EDMG part.

Spatial reuse related information may include whether inter-BSS spatialreuse may be applied; whether intra-BSS spatial reuse may be applied;and/or whether power based spatial reuse may be applied.

An EDMG packet may be transmitted (e.g., spoofed) as a beam trackingrequest (e.g., DMG beam tracking request) for RX training. An EDMG STAmay use the bits in the training length field of a beam tracking requestto perform additional EDMG signaling, e.g., by spoofing the beamtracking request. For example by setting the reserved bit to 1, it mayoverload the training length field to signal additional EDMGinformation. A STA may send an EDMG frame with one or more of thefollowing settings: a L-header Beam Tracking Requested field that may beset to 1; the packet Type field may be set to 0; and/or the traininglength field may request for Rx training of a desired length. By settingthe reserved bit to 1, the training length field may be spoofed intosending different information.

For example, a STA may send an EDMG frame with a L-header Beam TrackingRequested field that may be set to 1, the packet Type field may be setto 0, the reserved bit 46 may be set to 1, and/or the training lengthfield may be set to a value representing an EDMG parameter. The EDMGreceiver may determine that the sender may not request a RX beamtracking training and/or may use the bits in Training length field forEDMG signaling. For example, the EDMG receiver may determine that thesender is not requesting a RX beam tracking training and/or is using thebits in the training length field for EDMG signaling.

${{TXTIME}\left( T_{c} \right)} = {{\left( \left\lceil {\left\lceil \frac{Length}{42} \right\rceil \times \frac{672}{448}} \right\rceil \right) \times 512} + 4416}$

The above equation may be an example of how a STA (e.g., a legacy STA)may compute TXTIME. For example, the above equation may be an example ofhow a STA (e.g., a legacy STA) may compute TXTIME for a DMG SC PHY frame(e.g., with MCS=2). For a receiver (e.g., a legacy receiver), the STA(e.g., the legacy STA) may not (e.g., could not) decode the MAC headerfor receiving address (RA) and/or may not (e.g., could not) respond tothe beam tracking request. The STA (e.g., legacy STA) may generate aPHY-RXEND indication at the end of TXTIME. For example, the STA (e.g.,legacy STA) may generate a PHY-RXEND indication at the TXTIME after thestart of the packet reception.

To set the L-header Length field, the transmitter of the EDMG frame maydetermine the duration of the EDMG frame (e.g., EDMG automatic gaincontrol (AGC) and/or training sequences (TRN) field(s)) and/or may setthe value of the length field to approximate the duration. For example,EDMG sender may determine (e.g., may first determine) the duration of anEDMG frame (e.g., including EDMG AGC and/or TRN fields) as D (unit inT_(c)).

$\frac{D - 4416}{512} \leq \left\{ \begin{matrix}{3k} & {{case}\mspace{14mu} 1} \\{{3k} + 2} & {{case}\mspace{14mu} 2}\end{matrix} \right.$

where k may be the smallest integer that may satisfy the equation. Thesender may set the length as:

${Length} = \left\{ \begin{matrix}{{{42 \times \left( {{2k} - 1} \right)} + i},} & {i = {1{\ldots 42}\mspace{14mu}{if}\mspace{14mu}{case}\mspace{14mu} 1}} \\{{{42 \times \left( {2k} \right)} + i},} & {i = {1\mspace{14mu}\ldots\mspace{14mu} 42\mspace{14mu}{if}\mspace{14mu}{case}\mspace{14mu} 2}}\end{matrix} \right.$

An EDMG frame's duration may be greater than T_(c)×(2×512+4416)=3.09 us.In such a case, the frame may not be transmitted as a DMG BRP frame. Forexample, because the frame may not be transmitted as a DMG BRP frame,the EDMG frame may not be subject to aBRPminSCblocks SC blocks minimumlength requirement.

As provided above, an EDMG packet may be transmitted (e.g., spoofed) asa DMG beam tracking request for RX training. Use of the 5 bits ofTraining length field in L-header for EDMG signaling may be independentof the duration of the EDMG frame. For example, the use of the 5 bits ofTraining length field in L-header for EDMG signaling may be used forEDMG frames of any duration.

An EDMG packet may be transmitted (e.g., spoofed) as a DMG BRP-TX orBRP-RX packet.

The sender may send an EDMG frame with an L-header packet Type field setto 1, the reserved bit 46 set to 1, and/or the training length field setto a value representing an EDMG parameter. The EDMG frame may betransmitted (e.g., spoofed) as a DMG BRP-TX packet. The sender may sendan EDMG frame with L-header Beam Tracking Requested field set to 0, thepacket Type field set to 0, the reserved bit 46 set to 1, and/or thetraining length field set to a value representing an EDMG parameter. TheEDMG frame may be transmitted (e.g., spoofed) as a DMG BRP-RX packet.

The EDMG receiver may determine that the sender is not sending a DMG BRPpacket and/or uses the bits in Training length for EDMG signaling. Alegacy receiver may not be able to decode the MAC header for RA and/ormay not (e.g., will not) respond to the BRP frame. The receiver maygenerate a PHY-RXEND indication. For example, the receiver may generatea PHY-RXEND indication at the TXTIME after the start of the packetreception.

The equation below may show an example of how a STA (e.g., a legacy STA)may compute TXTIME for a DMG SC PHY frame (e.g., with MCS=2). A settingof training length field (N_(TRN)) may be used for EDMG signaling (e.g.,when the value of the length field is used to calculate a TXTIME). Tolet a STA (e.g., legacy STA) compute the TXTIME of the EDMG frame (e.g.,the same TXTIME of the EDMG frame), the EDMG sender may set the Lengthfield of L-header such that the TXTIME is approximately the same as theEDMG frame duration (e.g., EDMG packet frame duration). For example, thesetting of Length=42 k, 42 k+1, . . . 42 k+41 may result in a TXTIME(e.g., the same TXTIME) so the 5 bits signaled by the Length field(e.g., used as EDMG information) may be independent of the 5 bitssignaled by the Training length field (e.g., also used as EDMGinformation). The setting of Length field as provided herein may beindependent of the 5 bits signaled by the Training length field, eventhough the value of transmitted (e.g., spoofed) length field may beadjusted, e.g., based on the transmitted Training length field.

${{TXTIME}\left( T_{c} \right)} = {{{\max\left( {\left\lceil {\left\lceil \frac{Length}{42} \right\rceil \times \frac{672}{448}} \right\rceil,18} \right)} \times 512} + 4416 + {4992 \times N_{TRN}}}$

An EDMG frame may use the full 5 bits of Training length field inL-header for EDMG signaling. For example, an EDMG frame whose TXTIME(T_(c))≥T_(c)×(18×512+4416+4992×31)=95.67 us may use the full 5 bits oftraining length field in L-header for EDMG signaling. A shorter EDMGframe may be provided. For example, a shorter EDMG frame may be providedwhen the EDMG packet is transmitted as a DMG BRP-TX or BRP-RX packet, asdescribed herein. A shorter EDMG frame may be provided when the senderof the EDMG frame sets the training length as the EDMG information witha full resolution (e.g., 5 bits) and when the STA interprets the frameas being longer in duration than the actual short EDMG frame, e.g., asdescribed herein.

Use of a variation of fields (e.g., fields other than training Length ofthe L-header) to signal additional EDMG information may be provided.

The Beamtracking request and/or Packet Type may vary. For example, theBeamtracking request and/or Packet Type may vary by choosing one or moresignaling procedures, such as an EDMG packet being transmitted as a DMGbeam tracking request for RX training and/or an EDMG packet beingtransmitted as a DMG BRP-TX or BRP-RX packet. By varying theBeamtracking request and/or Packet Type, EDMG information (e.g.,additional EDMG information) may be signaled. For example, 1 more bit ofEDMG information may be signaled using examples described herein. Forexample, 1 more bit of EDMG information may be signaled by identifyingwhich type DMG packet is used to carry the EDMG packet: a beam trackingrequest for RX training and/or a BRP-TX or a BRP-RX packet. The MCSsignaled in L-header may be interpreted as EDMG information (e.g.,additional EDMG information).

A short EDMG frame may be provided.

The duration of an EDMG frame may be short when an EDMG frame istransmitted as a DMG BRP-TX or BRP-RX packet. The duration of an EDMGframe may be short to reduce the overhead of a transmission (e.g., ashort Sector Sweep frame (short SSW frame) which may 4 bytes while theoriginal SSW may be 26 bytes). If an EDMG frame is short and the EDMGframe is transmitted as a DMG BRP-TX or BRP-RX packet, MSBs of traininglength field may be set to 0. MSBs of training length field may be setto 0 to arrive to an overall duration approximating the duration of theshort EDMG packet. Setting the MSBs of Training Length field to 0 mayreduce the amount of EDMG information to be carried by the TrainingLength field.

The EDMG receiver may have an understanding that when the duration of anEDMG frame is less than a threshold, the information carried in traininglength may represent a lower resolution version of the EDMG informationcompared to the EDMG information (e.g., the same EDMG information) thatcould be signaled by the training length field in an EDMG frame (e.g., alonger EDMG frame). For example, a receiver of an EDMG packettransmitted as a DMG BRP-TX or BRP-RX packet may be based on thedifference between the real EDMG frame duration (e.g., acquired fromEDMG header) and minimum duration of a BRP frame (e.g.,T_(c)×(18×512+4416)) to calculate how many bits of EDMG information maybe signaled by the L-header Training Length field.

The sender of the EDMG frame may set the training length as the EDMGinformation with a full resolution (e.g., 5 bits). A third-party STA(e.g., a legacy STA) may interpret the frame as being longer in durationthan the actual short EDMG frame.

The terminology EDMG used herein may be replaced by Enhanced. Forexample, the corresponding EDMG feature may be an enhanced feature.

Features, elements and actions are described by way of non-limitingexamples. While examples are directed to 802.11 protocols, subjectmatter herein is applicable to other wireless communications andsystems. Each feature, element, action, or other aspect of the describedsubject matter, whether presented in figures or description, may beimplemented alone or in any combination, including with other subjectmatter, whether known or unknown, in any order, regardless of examplespresented herein.

Systems, methods, and instrumentalities have been disclosed for multiplechannel transmission in mmW WLAN systems. Multi-channel aggregation andchannel bonding may comprise, for example, multi-channel aggregation fora single transmitter/receiver pair or multi-channel aggregation andbonding for multiple transmitter/receiver pairs with frequency and spacebased multiple access. Multi-channel beamforming may comprise, forexample, one analog beam across two channels and analog circuits on eachchannel or a single analog circuit on both channels, one analog beamacross two channels and separate digital precoding schemes on eachchannel, one analog beam across a primary channel and separate digitalprecoding schemes on each channel or two analog beams on two channelsand separate digital precoding on each channel.

Although features and elements may be described above in particularcombinations or orders, one of ordinary skill in the art will appreciatethat each feature or element can be used alone or in any combinationwith the other features and elements. In addition, the methods describedherein may be implemented in a computer program, software, or firmwareincorporated in a computer-readable medium for execution by a computeror processor. Examples of computer-readable media include electronicsignals (transmitted over wired or wireless connections) andcomputer-readable storage media. Examples of computer-readable storagemedia include, but are not limited to, a read only memory (ROM), arandom access memory (RAM), a register, cache memory, semiconductormemory devices, magnetic media such as internal hard disks and removabledisks, magneto-optical media, and optical media such as CD-ROM disks,and digital versatile disks (DVDs). A processor in association withsoftware may be used to implement a radio frequency transceiver for usein a WTRU, UE, terminal, base station, RNC, or any host computer.

What is claimed is:
 1. A device comprising: a processor configured to:determine to transmit an enhanced directional multi-gigabit (EDMG)packet frame, wherein the EDMG packet frame comprises a legacy-header(L-header), and wherein the L-header comprises a length field, atraining length field, and a modulation and coding set (MCS); anddetermine values of the length field, the training length field, and theMCS, wherein when the values of the length field, the training lengthfield, and the MCS are used to calculate a transmitter time (TXTIME),the TXTIME is approximately a same duration as an EDMG packet frameduration; and a transmitter configured to: send the EDMG packet framewith the length field of the L-header set to the determined value, andwherein reserved bit 46 in the L-header is set to a value of
 1. 2. Thedevice of claim 1, wherein the device comprises a station or an accesspoint (AP).
 3. The device of claim 1, wherein the processor is furtherconfigured to determine a duration associated with the EDMG packetframe.
 4. The device of claim 1, wherein the EDMG packet frame comprisesat least one of an L-header packet type field, an L-header beam trackingrequested field, or a packet type field.
 5. The device of claim 1,wherein the EDMG packet frame is a DMG single carrier (SC) physical(PHY) frame.
 6. The device of claim 1, wherein the length field of theL-header set is less than a predetermined value.
 7. A method comprising:determining to transmit, by a device, an enhanced directionalmulti-gigabit (EDMG) packet frame, wherein the EDMG packet framecomprises a legacy-header (L-header), and wherein the L-header comprisesa length field, a training length field, and a modulation and coding set(MCS); determining values of the length field, the training lengthfield, and the MCS, wherein when the values of the length field, thetraining length field, and the MCS are used to calculate a transmittertime (TXTIME), the TXTIME is approximately a same duration as an EDMGpacket frame duration; and sending the EDMG packet frame with the lengthfield of the L-header set to the determined value, and wherein reservedbit 46 in the L-header is set to a value of
 1. 8. The method of claim 7,wherein the device comprises a station or an access point (AP).
 9. Themethod of claim 7 further comprising: determining a duration associatedthe EDMG packet frame.
 10. The method of claim 7, wherein the EDMGpacket frame comprises at least one of an L-header packet type field, anL-header beam tracking requested field, or a packet type field.
 11. Themethod of claim 7, wherein the EDMG packet frame is a DMG single carrier(SC) physical (PHY) frame.
 12. The method of claim 7, wherein the lengthfield of the L-header set is less than a predetermined value.